fix: normalize locked orchestrator health response bodies - #695

Problem

The contextual-orchestrator /healthz verifier already bounds streamed response bytes and makes cancellation best-effort, but it still called response.body.getReader() without normalizing synchronous reader-acquisition failure. A legitimately locked/non-stream-readable ReadableStream could therefore surface implementation-specific stream errors instead of one stable Noema transport diagnostic.

This is a Noema-owned health-response consumption/error-admission repair only. It does not move contextual-orchestrator service/provider/model routing, credentials, outbound authority, quarantine/security authority, release/deployment authority, or foreign domain truth into Noema.

Test-first RED

Test-only exact head: b66ee03c5a0ce57c7e346162353e4e7b852de0a0.

The hostile regression holds a real Response.body reader before verifyOrchestratorHealthz() attempts acquisition and requires the stable diagnostic:

contextual-orchestrator health response body is not stream-readable

A direct runtime reproduction against the protected implementation produced the underlying failure (TypeError: Invalid state: ReadableStream is locked), proving the current acquisition path leaked stream implementation detail. Hosted Actions for the test-only head entered the repository runner queue and had not been assigned when the minimal source repair was committed; the test-only commit remains immutable evidence.

Minimal repair

Current exact head: c9d526093e543167645383e937096fd089b337f8.

Only health-response reader acquisition is wrapped. Synchronous acquisition failure is normalized to the stable transport diagnostic. The existing 65,536-byte ceiling, optional caller-supplied deadline (no invented default timeout), fixed retained buffer, best-effort cancellation, fatal UTF-8, duplicate-key/JSON admission, orchestrator/free routing contract, and contextual-orchestrator ownership boundary are unchanged.

Verification

Final exact-head hosted CI/review/security/image gates are required before merge. No gate weakening, provider fallback, direct provider routing, self-approval, force-push, or destructive rebase is permitted.

Summary by CodeRabbit

• 버그 수정
  • 오케스트레이터 상태 확인 중 응답 본문 스트림을 읽을 수 없는 경우, 원시 오류 대신 이해하기 쉬운 오류 메시지가 표시되도록 개선했습니다.
  • 응답 스트림이 이미 사용 중인 상황에서도 오류가 일관되게 처리됩니다.